Autogenerated HTML docs for v1.5.0-rc2-g5355
diff --git a/config.txt b/config.txt index d8244b1..3f2fa09 100644 --- a/config.txt +++ b/config.txt
@@ -295,6 +295,16 @@ will enable basic rename detection. If set to "copies" or "copy", it will detect copies, as well. +fetch.unpackLimit:: + If the number of objects fetched over the git native + transfer is below this + limit, then the objects will be unpacked into loose object + files. However if the number of received objects equals or + exceeds this limit then the received pack will be stored as + a pack, after adding any missing delta bases. Storing the + pack from a push can make the push operation complete faster, + especially on slow filesystems. + format.headers:: Additional email headers to include in a patch to be submitted by mail. See gitlink:git-format-patch[1]. @@ -419,9 +429,13 @@ gitlink:git-push[1]. remote.<name>.receivepack:: - The default program to execute on the remote side when pulling. See + The default program to execute on the remote side when pushing. See option \--exec of gitlink:git-push[1]. +remote.<name>.uploadpack:: + The default program to execute on the remote side when fetching. See + option \--exec of gitlink:git-fetch-pack[1]. + repack.usedeltabaseoffset:: Allow gitlink:git-repack[1] to create packs that uses delta-base offset. Defaults to false. @@ -478,3 +492,8 @@ even if that push is forced. This configuration variable is set when initializing a shared repository. +transfer.unpackLimit:: + When `fetch.unpackLimit` or `receive.unpackLimit` are + not set, the value of this variable is used instead. + +
diff --git a/git-repo-config.html b/git-repo-config.html index 6616852..097a0a2 100644 --- a/git-repo-config.html +++ b/git-repo-config.html
@@ -962,6 +962,21 @@ </p> </dd> <dt> +fetch.unpackLimit +</dt> +<dd> +<p> + If the number of objects fetched over the git native + transfer is below this + limit, then the objects will be unpacked into loose object + files. However if the number of received objects equals or + exceeds this limit then the received pack will be stored as + a pack, after adding any missing delta bases. Storing the + pack from a push can make the push operation complete faster, + especially on slow filesystems. +</p> +</dd> +<dt> format.headers </dt> <dd> @@ -1219,11 +1234,20 @@ </dt> <dd> <p> - The default program to execute on the remote side when pulling. See + The default program to execute on the remote side when pushing. See option --exec of <a href="git-push.html">git-push(1)</a>. </p> </dd> <dt> +remote.<name>.uploadpack +</dt> +<dd> +<p> + The default program to execute on the remote side when fetching. See + option --exec of <a href="git-fetch-pack.html">git-fetch-pack(1)</a>. +</p> +</dd> +<dt> repack.usedeltabaseoffset </dt> <dd> @@ -1329,6 +1353,15 @@ set when initializing a shared repository. </p> </dd> +<dt> +transfer.unpackLimit +</dt> +<dd> +<p> + When <tt>fetch.unpackLimit</tt> or <tt>receive.unpackLimit</tt> are + not set, the value of this variable is used instead. +</p> +</dd> </dl> </div> <h2>Author</h2> @@ -1345,7 +1378,7 @@ </div> <div id="footer"> <div id="footer-text"> -Last updated 25-Jan-2007 02:23:47 UTC +Last updated 25-Jan-2007 07:59:39 UTC </div> </div> </body>
